-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Entra ID OAuthe2 token support #29032
Add Entra ID OAuthe2 token support #29032
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Swagger Validation Report
|
Compared specs (v0.10.9) | new version | base version |
---|---|---|
openapi.json | 2024-04-01(2a7ae6b) | 2024-04-01(main) |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️
LintDiff: 0 Warnings warning [Detail]
Compared specs (v2.2.2) | new version | base version |
---|---|---|
package-2024-04-01 | package-2024-04-01(2a7ae6b) | package-2024-04-01(main) |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
OperationId for put method should contain both 'Create' and 'Update' Location: HealthInsights/stable/2024-04-01/openapi.json#L141 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L1003 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L1210 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L1331 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L1980 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2007 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2043 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2047 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2051 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2055 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2082 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2086 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2090 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2797 |
|
Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: HealthInsights/stable/2024-04-01/openapi.json#L2802 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️
Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
} | ||
], | ||
"securityDefinitions": { | ||
"AADToken": { | ||
"type": "oauth2", | ||
"description": "The Azure Active Directory OAuth2 Flow", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Azure Active Directory is now Microsoft Entra ID https://learn.microsoft.com/en-us/entra/fundamentals/how-to-rename-azure-ad
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vicancy .
Is this what you meant ?
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
@marclerwick, @vicancy , @catalinaperalta , @weidongxu-microsoft CC: @koen-mertens |
specification/ai/HealthInsights/HealthInsights.OpenAPI/service.tsp
Outdated
Show resolved
Hide resolved
specification/ai/HealthInsights/HealthInsights.OpenAPI/service.tsp
Outdated
Show resolved
Hide resolved
….tsp Co-authored-by: catalinaperalta <catalinaperaltah@hotmail.com>
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
/azp run |
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
Pull request contains merge conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we adding AAD support to an existing api-version (that already serving customer)?
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
@weidongxu-microsoft |
"requestId": { | ||
"type": "object", | ||
"description": "An opaque, globally-unique, server-generated string identifier for the request.", | ||
"properties": { | ||
"response": { | ||
"$ref": "#/definitions/Azure.Core.RequestIdResponseHeader" | ||
} | ||
}, | ||
"required": [ | ||
"response" | ||
] | ||
} | ||
}, | ||
"required": [ | ||
"error" | ||
"error", | ||
"requestId" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see where these changes comes from.
There is no update to typespec file about these in this PR? -- maybe caused by the conflict in branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weidongxu-microsoft
Correct.
Fixed by merge from main.
OK. For a recent procedure change, you can add Though you need to resolve the conflict first. |
* Add AAD OAuthe2 token support * EntraIdToken * Update specification/ai/HealthInsights/HealthInsights.OpenAPI/service.tsp Co-authored-by: catalinaperalta <catalinaperaltah@hotmail.com> * remove suppression * update spec after merge --------- Co-authored-by: koen-mertens <138520871+koen-mertens@users.noreply.github.com> Co-authored-by: catalinaperalta <catalinaperaltah@hotmail.com>
Add support for AAD token credentials